Skip to content

Release candidate - 2026.03.000#209

Merged
anton-seaice merged 6 commits intomainfrom
rc-2026.03.000
Mar 17, 2026
Merged

Release candidate - 2026.03.000#209
anton-seaice merged 6 commits intomainfrom
rc-2026.03.000

Conversation

@anton-seaice
Copy link
Collaborator

@anton-seaice anton-seaice commented Mar 15, 2026

This change:


🚀 The latest prerelease access-om3/pr209-2 at 12e01ad is here: #209 (comment) 🚀


🚀 The latest prerelease access-om3/pr209-7 at bb18a6a is here: #209 (comment) 🚀

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr209-1 with commit aa20d46

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in spack.yaml, will be deployed to Gadi as:

  • 2025.08.002 as a Release (when merged).
  • pr209-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr209-1

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-om3-pr209-1 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr209-2 with commit 12e01ad

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in spack.yaml, will be deployed to Gadi as:

  • 2025.08.002 as a Release (when merged).
  • pr209-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr209-2

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-om3-pr209-2 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

@anton-seaice
Copy link
Collaborator Author

!update-configs

@github-actions
Copy link

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-om3-configs

Configurations Requested

Configurations requested from profile default:

  • dev-MC_100km_jra_ryf

  • dev-MC_100km_jra_ryf+wombatlite

  • dev-MC_25km_jra_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/23124751329

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr209-3 with commit a2a7fa2

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in spack.yaml, will be deployed to Gadi as:

  • 2025.08.002 as a Release (when merged).
  • pr209-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr209-3

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-om3-pr209-3 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

@anton-seaice
Copy link
Collaborator Author

Up to pr209-3 is not answer changing - see ACCESS-NRI/access-om3-configs#1219 (comment)

The rest of the changes will be answer changing

Trying this in the debugger from the PR build, it's missing source code. doing a local build and spack install --keep-stage makes the source code available too
Screenshot 2026-03-16 at 2 54 36 pm

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr209-4 with commit acb1025

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr209-5 with commit 050d00e

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

!redeploy

@anton-seaice
Copy link
Collaborator Author

@CodeGat - it seems like if two jobs try and install the same package at the same time they always conflict:

e.g. from the above two builds which were running concurrently

https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/23127192367/job/67172796218#step:15:2692

https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/23127472124/job/67173612949#step:15:2493

@CodeGat
Copy link
Member

CodeGat commented Mar 16, 2026

Ah, so fms concretized to the same hash in both, both tried to build it, and then they both failed? That might be quite a hard one to fix...there should be database locks that prevent that, if they're both attempting to write to that directory at the same time 😬 Has that happened before?

@anton-seaice
Copy link
Collaborator Author

anton-seaice commented Mar 16, 2026

Yeah i've done it several times.

It's kind of accidental mostly ... push a commit, forget something, quickly push a second commit and then you end up with two builds of very similar things. (Or the other one is push a commit, and change PR status in quick succession)

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr209-6 with commit 050d00e

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in spack.yaml, will be deployed to Gadi as:

  • 2025.08.002 as a Release (when merged).
  • pr209-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr209-6

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-om3-pr209-6 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

@anton-seaice anton-seaice marked this pull request as ready for review March 16, 2026 05:38
@anton-seaice anton-seaice requested a review from a team as a code owner March 16, 2026 05:38
@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr209-7 with commit bb18a6a

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr209-7 with commit bb18a6a

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in spack.yaml, will be deployed to Gadi as:

  • 2026.03.000 as a Release (when merged).
  • pr209-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr209-7

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-om3-pr209-7 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

@anton-seaice
Copy link
Collaborator Author

This is ready for review - there should be repro results soon in

ACCESS-NRI/access-om3-configs#1220 (comment)

and

ACCESS-NRI/access-om3-configs#1219 (comment)

Both will be answer changing

@dougiesquire
Copy link
Collaborator

I also reopened ACCESS-NRI/access-om3-configs#1217 just to check/document that things still run after the gtracers update

Copy link
Collaborator

@dougiesquire dougiesquire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @anton-seaice. I have just discovered another issue in WOMBATlite that can lead to an overflow. But I've only seen this manifest at 0.1deg, so hopefully it doesn't occur in the 25km IAF run.

@anton-seaice
Copy link
Collaborator Author

Have you tried running OM3 - MC_25km+wombatlite ?

@dougiesquire
Copy link
Collaborator

Have you tried running OM3 - MC_25km+wombatlite ?

I've run it for 10 years, though admittedly with an older version of WOMBAT. I will hopefully have a fix today if we want to wait

@dougiesquire
Copy link
Collaborator

If I haven't got the WOMBAT issue fixed by 1pm, let's go ahead. I'm hopeful the issue won't occur at the OM3 resolutions we currently support. And if it does end up occurring in Andrew's run we can always just turn WOMBAT off.

@dougiesquire
Copy link
Collaborator

dougiesquire commented Mar 17, 2026

@anton-seaice please go ahead. We're not going to get the WOMBATlite issue resolved today

@anton-seaice anton-seaice merged commit df1d280 into main Mar 17, 2026
17 of 18 checks passed
@anton-seaice anton-seaice deleted the rc-2026.03.000 branch March 17, 2026 02:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update target Set -grecord-gcc-switches Upstream model component update, tweaking the docs Debug builds broken Stack trace information missing

3 participants